projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6890444) | patch
ostbuild: Pull patches from specified patches git repository
authorColin Walters <walters@verbum.org>
Tue, 28 Feb 2012 11:40:35 +0000 (06:40 -0500)
committerColin Walters <walters@verbum.org>
Tue, 13 Mar 2012 14:39:25 +0000 (10:39 -0400)
commitd8eebaa2d1935aa19d6d683cac5f7c5868876769
treee88042a4a20a2103f346f3f8743dcc045418b864tree | snapshot
parent6890444f28aedace99a58f55b02efbd5d0b6465dcommit | diff
ostbuild: Pull patches from specified patches git repository

We need to be more formal about where we get patches from, and more
specifically what version.  Let's assume they're also stored in a git
repository that we fetch, instead of copying them from "wherever the
manifest is".

This meshes nicely with splitting between manifest.json and
snapshot.json.
gnomeos/3.4/manifest.json diff | blob | history
src/ostbuild/pyostbuild/builtin_build.py diff | blob | history
src/ostbuild/pyostbuild/builtin_resolve.py diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.